home *** CD-ROM | disk | FTP | other *** search
- Input file structure:
-
- VARIABLES: // Two slashes comment rest of line.
- <variable-name>=<double> // No spaces here
- [ ... ]
-
- FRAME [integer] // Whitespace where shown here.
- // Tabs, spaces, returns are all whitespace.
-
- [ FRAMES <integer> ]
- [ <variable-name> TO <double> [ MODE <integer> ] [ FRAMES <integer> ] ]
- [ <variable-name> RANDOM <double> <double> [ FRAMES <integer> ] ]
- [ <variable-name> SIN <double> <double> <double> <double> [ FRAMES <integer> ] ]
- [ ... ]
-
- END
-
- You may have one VARIABLES: block, but many FRAME blocks. The FRAMES
- command should only appear at the top of a FRAME block, otherwise the
- parser will probably think it's a FRAMES modifier to the previous command.
-
-
- Data-file structure:
-
- AAT understands little about the structure of your renderer's input-file.
- It makes a couple of assumptions:
-
- The banner inserted at the top uses /* and */ to signal a comment. If your
- renderer doesn't do this, you can yank the banner altogether, or change the
- text in the delimiters only. I'd prefer the second, obviously.
-
- If your renderer uses $ as a meaningful character, you'll have to change
- the program's #define REPCHAR line.
-
- AAT copies from the data-file to a generated file, character-for-character
- until it enocounters a $ symbol. Then, it reads to another $ or a
- whitespace. Then, the value of the named variable is written to the output
- instead of the $ and the text following.
-
-
-